-
Notifications
You must be signed in to change notification settings - Fork 141
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
update mining-device-sv1 to tracing #1294
update mining-device-sv1 to tracing #1294
Conversation
Bencher Report
Click to view all benchmark results
|
Bencher Report
Click to view all benchmark results
|
Bencher Report
Click to view all benchmark results
|
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #1294 +/- ##
==========================================
+ Coverage 19.30% 19.36% +0.06%
==========================================
Files 164 164
Lines 10849 10815 -34
==========================================
Hits 2094 2094
+ Misses 8755 8721 -34
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
8d9ed93
to
0600602
Compare
obrigado pela contribuicao @devworlds 🇧🇷 rebasing with latest |
the commit history is a bit messy we do things, then we add extra commits to undo them out of regret of what we did in previous commits the following commits shouldn't exist @devworlds could you squash those changes into fewer commits that are restricted to the changes that we aim to introduce with the PR? |
commit 0600602 is weird because it's changing things on other crates ( this PR shouldn't need to touch any crate outside of |
@devworlds apologies for the limited issue description, it's been fixed
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
obrigado pela contribuicao @devworlds 🇧🇷
I left some comments on how we can proceed with this PR
thanks for clarify, i will update the things! |
sure! |
oh, sure! this was changed cause when run the command cargo clippy, was asked to run a command to "solve" the warnings, so i run it, but now i know, that i do not need to change nothing outside the mining-device-sv1. |
its okay to open another PR, more clean? |
you can always rebase the commit history on https://medium.com/nona-web/cleaning-up-commit-history-with-git-rebase-61dc41d2829c |
-> #1309 |
Hello, this is my first open-source pr, basically i follow what was asked.
update mining-device-sv1 from println! to info! using tracing following mining-device as example.
i don't update the eprintln! cause in the issue was mencioned only the println!
well, i hope this help.
the issue: #1286